Logux DB refactoring - #339

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yaml → npm/sqlocal@0.18.0 → npm/coincident@1.2.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/coincident@1.2.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Confidence: 0.90

Location: Package overview

From: core/package.json → npm/jsdom@30.0.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jsdom@30.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Notes: High-risk design for supply-chain/security review: although the core parsing is delegated to an embedded WebAssembly module, the JavaScript wrapper conditionally calls eval() on substrings derived from the untrusted input string (triggered by quote heuristics). This creates a direct path from attacker-controlled text to arbitrary JavaScript execution. Additionally, parse failures embed input excerpts into thrown errors (possible information disclosure) and large inputs can trigger WASM memory growth (DoS). This module should be treated as unsafe unless the calling context strictly guarantees that inputs are fully trusted and non-executable (or the eval behavior is removed/disabled).

Confidence: 0.70

Severity: 0.86

From: pnpm-lock.yaml → npm/drizzle-kit@0.31.10 → npm/vite@8.2.1 → npm/postcss-load-config@6.0.1 → npm/tsx@4.23.9

ℹ Read more on: This package | This alert | What is AI-detected potential malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Given the AI system's identification of this package as malware, extreme caution is advised. It is recommended to avoid downloading or installing this package until the threat is confirmed or flagged as a false positive.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tsx@4.23.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.